BIP39 seed phrase generator

BIP39 Seed Phrase Generator

Derivation Path

For more info see the BIP44 spec.

Purpose

Coin

Account

External / Internal

The account extended keys can be used for importing to most BIP44 compatible wallets, such as mycelium or electrum.

Account Extended Private Key

Account Extended Public Key

The BIP32 derivation path and extended keys are the basis for the derived addresses.

BIP32 Derivation Path

For more info see the BIP32 spec

Client

BIP32 Derivation Path

Bitcoin Core

Use path m/0'/0' with hardened addresses.

For more info see the Bitcoin Core BIP32 implementation

Multibit

Use path m/0'/0. For change addresses use path m/0'/1.

For more info see MultiBit HD

Block Explorers

Use path m/44'/0'/0'. Only enter the xpub extended key into block explorer search fields, never the xprv key.

Can be used with: blockchain.info

For more info see the BIP49 spec.

Purpose

Coin

Account

External / Internal

The account extended keys can be used for importing to most BIP49 compatible wallets.

Account Extended Private Key

Account Extended Public Key

The BIP32 derivation path and extended keys are the basis for the derived addresses.

BIP32 Derivation Path

For more info see the BIP141 spec

BIP32 Derivation Path

Script Semantics

For more info see the BIP84 spec.

Purpose

Coin

Account

External / Internal

The account extended keys can be used for importing to most BIP84 compatible wallets.

Account Extended Private Key

Account Extended Public Key

The BIP32 derivation path and extended keys are the basis for the derived addresses.

BIP32 Derivation Path

Derived Addresses

Note these addresses are derived from the BIP32 Extended Key

Encrypt private keys using BIP38 and this password: Enabling BIP38 means each key will take several minutes to generate.

Use hardened addresses

Table
CSV

Path	Address	Public Key	Private Key

Advanced info

Entropy

Entropy values should not include the BIP39 checksum. This is automatically added by the tool.

Entropy values must be sourced from a strong source of randomness. This means flipping a fair coin, rolling a fair dice, noise measurements etc. Do NOT use phrases from books, lyrics from songs, your birthday or street address, keyboard mashing, or anything you think is random, because chances are overwhelming it isn't random enough for the needs of this tool.

Do not store entropy.

Storing entropy (such as keeping a deck of cards in a specific shuffled order) is unreliable compared to storing a mnemonic. Instead of storing entropy, store the mnemonic generated from the entropy. Steganography may be beneficial when storing the mnemonic.

The random mnemonic generator on this page uses a cryptographically secure random number generator. The built in random generator can generally be trusted more than your own intuition about randomness. If cryptographic randomness isn't available in your browser, this page will show a warning and the generate button will not work. In that case you might choose to use your own source of entropy.

You are not a good source of entropy.

Card entropy has been implemented assuming cards are replaced, not drawn one after another. A full deck with replacement generates 232 bits of entropy (21 words). A full deck without replacement generates 225 bits of entropy (21 words).

PBKDF2

What is PBKDF2 (Password Based Key Derivation Function 2) ?

Please refer to this wikipedia article for more detail. Mail about PBKDF2 security here.

Wallet software that implement BIP39 only use 2048 iterations as a norm. Increasing this parameter will increase security against brute force attack, but you will need to store this new parameter. However, as long as you back up your BIP39 seed there will not be risk to lost your fund. To access them with custom PBKDF2 iterations, use this file (or other) to compute your targeted BIP39 seed.

Using less than 2048 PBKDF2 iterations is insecure without strong optional BIP39 Passphrase.